-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(RELEASE-400): adds check-data-keys task in release pipeline #720
base: development
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
c12a590
to
c7747cd
Compare
d339fc4
to
2e89177
Compare
5d88a5c
to
d7ef3c8
Compare
c9ccb55
to
7ca3e22
Compare
@@ -49,8 +57,7 @@ | |||
}, | |||
"productName": { | |||
"type": "string", | |||
"description": "The product name e.g. exampleproduct ", | |||
"pattern": "^[a-z]+$" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/workspace/data/5c52c6c8-898a-4a85-93b2-9336e6601e52/data.json::$.fbc.productName: 'testProductName' does not match '^[a-z]+$'
Just removing for time being to get E2E to pass.... I would say we can remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe just relax it to allow capital letters? Or modify e2e to contain lowercase in the name? That should be easy. Maybe just this here? https://github.com/konflux-ci/e2e-tests/blob/fd26460f5d0035b0bffe699513c558be8588b209/tests/release/pipelines/fbc_release.go#L347
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hit this with some of the advisory keys too. I am fine with either removing it (the pattern, not the description) or modifying like Martin said so long as it is not too restricting such that users are going to fail on this
7ca3e22
to
a43b87a
Compare
a7d2762
to
7c51620
Compare
5c052db
to
3deabf8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E2E results may be interesting on this one 😂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the same as rh-push-to-registry-redhat-io
but + advisories, so I think it should also have the systems that one has
pipelines/rh-push-to-registry-redhat-io/rh-push-to-registry-redhat-io.yaml
Outdated
Show resolved
Hide resolved
value: | ||
- mapping | ||
- pyxis | ||
- sign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see signing tasks in this pipeline, but I do see slack stuff
/ok-to-test |
- name: data | ||
workspace: release-workspace | ||
runAfter: | ||
- collect-data |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In rh-advisories, this has verify-enterprise-contract in runAfter. Not sure which one is more correct, but they should do the same - and if run after verify-enterprise-contract is correct, then perhaps it should be used in other pipelines that have it as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They all should be run after collect-data
... Will update the push-to-cdn
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comment is about rh-advisories ;) Not sure what you mean by "will update push-to-cdn" - that's a task. Which pipeline are you talking about?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused as rh-advisories
has populate-release-notes-images in its run after for check-data-leys.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, and we need to keep it that way AFAIK because it checks some of the keys the populate-release-notes-images task adds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need to keep it that way AFAIK because it checks some of the keys the populate-release-notes-images task adds
You mean if we checked the keys after populate-release-notes-images, it might not pass? But we just discussed elsewhere that the schema does include the releaseNotes.content.images, right? So it should be fine?
But I'm not sure who was even proposing we do the check after populate-release-notes-images here, certainly not me.
My original question still stands: rh-advisories has verify-enterprise-contract in runAfter. Do we want that, or do we want collect-data? (Of course if we decide to have it after populate-release-notes-images in rh-advisories, this question would no longer be relevant.)
8da7b70
to
5cd1579
Compare
5cd1579
to
083ef6f
Compare
This commit adds the check-data-keys task into the release pipelines to ensure validation of required data keys. Signed-off-by: Sean Conroy <sconroy@redhat.com>
083ef6f
to
003c505
Compare
@seanconroy2021: The following test has Failed, say /retest to rerun failed tests.
Inspecting Test ArtifactsTo inspect your test artifacts, follow these steps:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service-catalog:konflux-e2e-tests-catalog-ct8tp |
This commit adds the check-data-keys task into the release pipelines to ensure validation of required data keys.
Link